Amiga Plus 1996 #6/Amiga Plus CD - 1996 - No. 06.iso/pd/netz/hbbs/todo.txt

Text File | 1996-06-29 | 14KB | 360 lines

ToDo
====

fix problem (not bug) with @^@ codes and special formatting..  I'm using sprintf()
to do the formatting at the moment, so you just use std 'C' % formatting options
like %-15s (-> @^-15s^ComputerType@ in a screen ), but if the item you are printing
is more that than the amount of chars you specify it will not chop the rest off...
the downside to this is that if you designs screens (like raider has done for me)
they kind of mess up when you use long strings etc...

create an Error Watcher program, which sets up a port called "HBBS_Error_X" (where x is
a number, so you can have more than one port..), then change hbbs_LogError()
so it checks for those ports and sends them the details of the error in a message.
Then a sysop can have a window pop up on his screen with the error... (great for
finding problems with a setup..)  you could also have a program like SendOLM in
HBBS:Utils that checks to see if a co-sysop or sysop is on-line and sends them the message
too!  Cool....

Fix bug with OLM's and FrontEnd (when you're typing in a node password)

Implement Extra#? settings in structures.h

Implement Calls Allowed checking

New user Timelimit needs to be added somewhere (probably same place as NewUserConf...)
or could be withing the NewUser door...

check that AddCreds door can accept a conference number as a parameter to allow
for easy implementation of conference accounting..

make the TagFile door call a door called "OKToTag" with the conference num and filename as
parameters (for easy implementation of conference accounting and file restriction doors)
(like passworded files..)

Add Ctrl-C checking to DisplayScreen() and DisplaySpecialScreen()

Multinode chat door

Add File Password support (i.e. change tag door so search for a config file
that has a list of filenames, and passwords. (maybe a confnum too, depends wether you'll ever
have files of the same name in a difference conference..)

  Hmm, example config file (HBBS:Doors/System/TagFile/PasswordedFiles.CFG)

  Name_1=HydraBBSA10.LHA
  Type_1=CONF ; could be CONF, or SYSTEM (i.e. filename can be full path if using SYSTEM)
  Conf_1=5 ; HBBS Conf if CONF is used
  Level_1=250 ; if you are below this access level you will be asked for the Password
  Password_1=BETA ; where BETA is the actual password..

oh, and we also need another config file with a list of files that cannot
be downloaded except by the sysop.. ie. HBBS:Doors/System/TagFile/RestrictedFiles.CFG

  File_1=HBBS:System/Data/User.Data
  File_2=HBBS:Doors/System/TagFile/TagFile

Fix ctrl-x/up/down with GL_NODISTURB (door writers should not use GL_HISTORY until
this is fixed if possible..)

have a cool DOOR_WriteTextSpecial() function that given the corrent flags, timeouts
and string will display text on the screen as if it was coming from a 300baud modem
as per the "wargame" film.

Write a GUI for AutoComment and finish it!

move some strings from N_ND->NodeSettings to the appropriate door's config file
(e.g. usernameprompt should really be in FrontEnd.CFG...)

make it so that the node watch windows can be opened on a different public screen
to that of the Control Program

add routine to show all availiable public screens and use instead of a string gadget
when selecting screen to appear on.
(unless reqtools has this option...)

add a routine to copy a list into HBBSCommon.c

implement ConfAcs files, add checkuser to get it to check for a users confacs file
beging present, if not write a msg to a log file
(refs: Access/Levels/Level_List, System/Data/ConfAcs/#?)

network mail! yeah!

option for sysop to set N_ND->DoorLogOverride=TRUE (button on GUI)

option on CommandPrompt door to log all commands user types (like DoorLog in /X)
  (DoorLog in HBBS is a bit different...)

startup log

error checking on ConfAcs loading... (problems if file does not exist)

sentby ask door (see userdata structure)

sentby attach to uploads

spell checker on messages!

add a file_id.1 into files with a one-line description..

util to convert aminet cd dirs to hbbs filelistings..

and a 1 id to the filelist format same as F but with only a one-line description..

create docs with a list of /X config settings in and show the user
what the same things are in HBBS

change watch window font depending on conference..

you can currently write a USER mail to ALL !

have it so that you can enable different logs for different users.  for instance,
say you have a user who's a bit dogdey you might want to enbale the doorlog for
him, but not for everyone else...  Coooooooooooool!


doubleclicking on a user name in a listview window should bring up an
account editor with the users details in! :-)

make the G door accept NOPROMPT as an option.

ban ;'s from user handles and names (and anything else that might go into a config
file :-)

create a ST door so that sysop's can flag files for other users..
--> you can do this anyway by editing the files in HBBS:System/Data/Taggedfiles/#?

add QUIET parameter to Tag_File

make node wait for SIGBREACK_CTRLC or sommat in the getline loop..

add a GL_KEEPPROMTIFBLANK which will return the prompt string (if specified) in
N_ND->CurrentLine if the user delete's the prompt string and leaves a blank line!

make node, settings, and configure windows pop to front if already open.

add an [U]pload to the editor program..!

set a button on the control to open up a node's "Settings" window!

change the door commands and how doors are run..

  Ideas

  call <Name>_Door_<n>  <name>_Data_<n> so it avoid confusion
  when using something like SCREEN or ECHO for a door type.

  also you need to be able to specify the paramters that were typed at the bbs
  prompt as options for doors, be you must also be able to add your own options
  to them as well,  example:

  FR_Type_1=NORMAL
  FR_Data_1=HBBS:Doors/User/FileReverse/FR.HBBS {nodenum} {bbsoptions} CONF

  FRS_Type_1=NORMAL
  FRS_Data_1=HBBS:Doors/User/FileReverse/FR.HBBS {nodenum} {bbsoptions} HOLD

  where {nodenum} is replaced by the node number, {bbsoptions} are replaced by the
  options that were typed at the bbs prompt..  so, if a user on node 3 types

  FR N -2

  the actual command executed would be

  HBBS:Doors/User/FileReverse/FR.HBBS 3 N -2 CONF

  much better than just appending the params to a program.  also like this
  you can place the parameters in any order you like.. thus being able to cope with
  far more programs and it also makes the program more flexible.  it also
  reduces the amount of seperate doors you might need..

  also I need a DOOR_Continue(TRUE/FALSE) and associated
  N_ND->DoorContinue.

  if a door sets door continue to false the next door will not be run
  if the configuration for a door has more than one door associated
  with the command.

  e.g.

  the download door a) calls the HBBS:Doors/<blah>/Download.HBBS, then
  it would b) call the door HBBS:Doors/<blah>/QuickStats.HBBS.

  obviosly, the download door might be cancelled before we actually
  transfer some files, so it would set DoorContinue to FALSE then
  the quickstats door would not be run..

change GetLine()

  Ideas..

  instead of going TRUE,TRUE,0,blahh..  use FLAGS

  so we need these flags

  EDIT      // left/right cursor keys and backspace + delete
  HISTORY   // allow cursor up/down to gothrough the history
  DISPLAY   // display text on screen at all ?
  LINEWRAP  // if reached maxlen and last key pressed was a non space
            // char then copy all data back to the previous space char
            // to N_ND->CurrentLineWRAP and return IN_GOTLINE
  NORETURN  // does not print a "\r\n" when the user presses return
  IMMEDIATE // returns when the user has typed in MaxLen chars
            // don'tuse with linewrap :-)
            // use immediate and noreturn for hoykey support.  -> COOL

  also we need to be able to prompt the user with a default string for an option.

  timeout is in micros

  An example prototype might be

  GetLine(Flags,PasswordChar,MaxLen,TimeOut,PromptStr);


  the above example takes less params then the current version *AND* offers more
  scope
  -------------

existence of tagged files must be verifyied when the saved tags are loaded in
again (when a user logs on, see node_input.c)

change str_CtrlScrnName from a set length variable to a string pointer, and allow
changing between a public screen name and "CtrlScrn", that way you can hbbs on a WB
screen.

Use this function more!!!
-> HBBS_LogError(BBSGlobal->ErrorLogFile,ERR_GENERAL,outstr,TYPE_WARNING);

add options for /X help for sysop's and users to help them change between systems
(i.e. when a sysop presses F10 wanting to log a user off tell him to press
SHIFT+F10 instead of just F10..etc... do the same sort of things for door commands..)

when a node starts it must check the playpen and work for file and move/delete them
accordingly. (check id of last user that called from log files..)

Add NamesNotAllowed files to Node_XX directories, don't make it a config file,
just have a list of names so it's easier to add/remove names rather than having to
change name_xx = name_xx when you remove a name from the middle of the list.

Add tones and tonnes of error messages that are logged in the logfile..

Add DOOR_HuntScreen() to door library to search for screens in the node
directory and then the screens directory, with option for adding a specified access
level.  e.g. DOOR_HuntScreen("Files",20); where it would search for Files_20.TXT...

make HBBS_SaveUser() or whatever to search for users with a status of
user_overwritable

implement LanguageName_XX and LanguageExtn_XX for screens...

change ALL strncpy()'s to strNcpy()!!!  IMPORTANT!! (strncpy() does not always null terminate strings..)

add option "SkipOK" to Device config so that if you have a weird modem you
can tell the bbs not to wait for the OK string after commands..

when control is opened on a 16 colour screen set the first 8 colours
to the standard ANSI colours and set the next 4 colours to the usual WB colours.
then set the dripens for drawing windows/gadgets etc to point to the usual colours
--> nearly done, sets palette and dri-pens, but just can't get the background
    of the screen and windows to be anthing other then colour 0... Hrmmm..


get the Node program to run a door just after frontend called "Speed_XX.HBBS", where
xx is replaced by the baud rate of the caller..

create caller logs (ie, when a user logs on and at what speed and all that shite..

add timeout on doors,  best place would be where NODE looks at messages coming
from the door program,  you could set a timer when the door has started (when you get
a doorstart IO message) and see if it times out, if it does then cancel running that
door.  Also you'd have to reset the timer everytime the node received a message
from the door,  BUT, file transfers will be sending all their data via messages
so you could only reset the timer on bog standard messages,  perhaps set up a new
type of message for use only by transfer protocols that would be skipped...

have a button in the node's settings window to manually stop a door.  This is cool
if a door has crashed and you want the system to continue..  also the timeout on the
door function would need to call the same cleanup function.  was thinking of being
able to pass the a pointer to the door you want to cancel as a parameter, to
HBBS_CleanupDoor()

have option for sysop, so that they can choose to strip all ansi colour changes
from the watch window, thus speeding up the user's display. (this would also be better
if the sysop was using watch windows on a 2,4 or 8 colour screen.)

add time, bytes etc to the HBBS_ModifyString() function in HBBSNode.C.
--> done, still need to add bytes to ModifyString() tho.

create a history file for the wall with the users handle on it..

add in developer docs and specify the point that you can't have config item options
  as follows

  Item_XX
  Item_XX_Blah

  as HBBS_RemoveCfgItem("Item_#?") would remove ALL the items above..

  oh, and don't use ?'s or #?'s in item names :-)

state importance of taking a copy of N_ND->CurrentLine before passing it to another
door as a parameter, in developer docs...

have userhandle, and status (u/l'd d/l'd pw failed, scanned, paged etc) all on the
window title of a watch screen or window..
--> handle, group and speed are displayed..


ToDone :-)
======

fix bug with a closed console screen sometimes crashing the system, to check do this:
load up node3, close the screen, load up term. use nullmodem.device, unit 7.  and
try and log in.  it crashed when you press return after typing in a correct handle..
--> done, it was Node_Console.c's SetWatchTitles() on a closed window...

add @^PAUSE_TIMEOUT^@ with options timeout length
--> done, it's @^TPAUSE^<seconds>@

make it so that if you pass 0 as a buffersize to HBBS_CopyFile() then it'll use
a default value. (sysop specifyable...!! cool idea!)
--> done, see BBSGlobal->CopyBufferSize

abort prompt when cancelling message
--> done

implement bbsglobal->CallsEver
--> done

fix who door, long names/handles cause it to fuck itself..
--> done

if settings window is open, bring it to front
--> done

write the following to the CallersLog file when a user logs off
uploads, downloads, ulbytes, dlbytes, nukes, pages, msgs read, msgs written
then it'll be dead easy to provide statistics for bulletins etc!
--> done

fix small bug in @^SYSDOOR@ANNOUNCE OFF@, the command the gets run has two spaces
between the node number and the OFF parameter instead of one.
e.g. 19-JUN-1996 18:56:16 Handle: hydra, Conf: Amiga Warez, Door: HBBS:Doors/System/Announce/Announce.HBBS 3  OFF
--> done

option to have a list of users that dooroverride is set to on for
(i.e.  a list of suspect users that have been trying to play around with your bbs!)
-->done, created SetSuspect system door

option for getline, GL_NODISTURB.  needs to make it so that if you specify a maxlen
then it means it musn't move things on the same line after the input position
(e.g.  see why on the sent door)
 need to be able to have  "Enter Name: [            ]", at the moment the ] gets moved
--> done

RAW input for doors (i.e. show a text fiel and let users press keys to pause it etc..)
--> done, see DOOR_CheckRaw(Flags);